Wearable Device Zone Group Control

ABSTRACT

Configuration information and selectable grouping options associated with the plurality of zones is displayed, for example, on a wearable device. Selection of a first selectable grouping option is received and in response a configuration change is transmitted. The configuration change may comprise information indicating a first zone is to join a zone group with a second zone of the plurality of zones. Updated configuration information is received indicating that a media playback system includes the zone group comprising the first zone and the second zone. The updated configuration information is displayed on the wearable device.

CROSS REFERENCE TO RELATED APPLICATION

This disclosure claims the benefit of priority as a continuation under35 U.S.C. § 120 to U.S. application Ser. No. 15/273,246 entitled“Wearable Device Zone Group Control” filed on Sep. 22, 2016, which is acontinuation of U.S. application Ser. No. 14/682,547 entitled “WearableDevice Zone Group Control” filed on Apr. 9, 2015, the contents of eachof which is hereby incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when SONOS, Inc., filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The Sonos Wireless HiFi System enablespeople to experience music from many sources via one or more networkedplayback devices. Through a software control application installed on asmartphone, tablet, or computer, one can play what he or she wants inany room that has a networked playback device. Additionally, using thecontroller, for example, different songs can be streamed to each roomwith a playback device, rooms can be grouped together for synchronousplayback, or the same song can be heard in all rooms synchronously.

Given the ever growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIGS. 5A-5C illustrate example control interfaces.

FIGS. 6A-6C illustrate example grouping control interfaces.

FIG. 7 shows an example control system for a media playback network.

FIG. 8 illustrates an example controller application.

FIG. 9 illustrates an example data flow diagram depicting a flow of databetween the wearable device, controller device, and playback system.

FIGS. 10-13 show flow diagrams that illustrate example methods tofacilitate zone grouping and control in a playback system.

The drawings are for the purpose of illustrating example embodiments,but it is understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

As disclosed herein, a wearable device, such as a watch, wristband,bracelet, among other possibilities, can be used with another electronicdevice to control and/or manage playback of media content via a playbacksystem. For example, a computing device, such as the wearable device orother mobile device, may have installed thereon a controller applicationto provide a controller interface on the computing device for a mediaplayback system. One or more icons and/or other representations providedvia the controller interface can be used to control operation and/orconfiguration of the media playback system. In some examples, thecomputing device may communicate with the media playback system viaanother device, such as a mobile device.

In one example, a first controller application is executing on a mobiledevice. A second controller application is executing on a wearabledevice. Controlling playback of media content in a particular playbackzone may be performed via the first controller application executing onthe mobile device and/or the second controller application executing onthe wearable device, alone or in communication together. For instance,control of playback may involve the first controller applicationreceiving from the second controller application, a command provided viathe second controller application, and responsively communicate with themedia playback device to execute the command. The command may involveone or more of a selection and/or control of playback navigation to viewa particular playback zone, playback or stop playback of a media item inone or more playback zones, a change in playback zone configuration,among other possibilities.

Some examples disclosed and described herein involve providing, on adisplay of a computing device (e.g., a wearable device, a mobile device,other computing device, etc.), playback controls for a particularplayback zone of a media playback system, more of which is describedbelow. The playback controls may be used to control playback of mediacontent in the particular playback zone.

In one example, a graphical display of the computing device may displayan indication of a playback zone and control elements selectable forcontrolling media playback in the playback zone of a media playbacksystem. The control elements may include control elements selectable to,among other things, cause media content to be played, paused, skippedforward, and/or skipped backward, etc. The control elements may alsoinclude control elements to modify a playback volume in the playbackzone, for example. Control elements may also facilitate editing ofzones, grouping of zones, etc.

In one case, the playback zone for which the control elements aredisplayed may be a playback zone that was last accessed using thecomputing device, a playback zone that the computing device determinesis nearest to the computing device, or a predetermined default zone thatis displayed when the computing device establishes communication withthe media playback system. Other examples are also possible.

In certain examples, a selection of one or more of the control elementsmay be received via the computing device (e.g., from the wearable devicevia the mobile device and/or other computing device, etc.). Based on theone or more control elements selected (e.g., received as an input fromthe wearable device), the computing device communicates with theplayback system to cause a particular playback zone of the playbacksystem to go from a first playback state to a second playback state. Forinstance, if the playback zone is in a paused playback state, aselection of a control element to play media content in the playbackzone will cause the playback zone to begin playing media content, orcontinue playing media content that was previously paused. In someexamples, the playback system (e.g., the affected playback zone(s) inthe playback system) may return an acknowledgement (e.g., updatedconfiguration information) to the computing device in response to theselection sent by the computing device. Other examples are alsopossible.

In another aspect, a computing device, such as the mobile device and/orthe wearable device, is provided. The computing device includes aprocessor, and memory having stored thereon instructions executable bythe processor to cause the computing device to perform functions. Thefunctions include causing a graphical display to display an indicationof a playback zone and at least one control element. The at least onecontrol element controls the playback state of the playback zone. Thefunctions also include receiving by the computing device a selection ofone or more of the at least one control element, and, based on thereceived selection, communicating with a playback system (e.g., one ormore playback devices in the playback system) causing the playback zoneto enter a second playback state. In some examples, the computing deviceis or communicates with another computing device (e.g., a smart phone,laptop, personal computer, and/or other controller device) which servesan intermediary to relay instructions, configuration information, etc.,and receive acknowledgements, configuration update information, etc., inresponse from the playback zone.

Some embodiments described herein relate to facilitating zone groupingand adjustment of zone representation in a playback system dependentupon a zone's grouping status. For example, a first computing device(e.g., a wearable device) interacts with a second computing device(e.g., a smart phone, laptop, and/or other controller device) to receivezone configuration information from the playback system, provide zonegrouping instructions to the playback system, and receive an updatedzone configuration from the playback system. Display of playback systeminformation via an interface of the first and/or second computing deviceis updated based on the updated zone configuration, for example.

In some embodiments, a computing device includes a communicationinterface configured to exchange data and commands between the computingdevice and a wearable device to control a playback system. The examplecomputing device includes a processor configured to receive and processinput in conjunction with the communication interface to facilitatecontrol of the playback system. The example processor is configured toaffect display and control of a user interface configured for a displayof the wearable device. The example user interface forms a controlinterface to affect a configuration of playback devices in the playbacksystem, and each playback device in the playback system is associatedwith at least one zone. The example control interface is arranged todisplay at least a first item and a second item. The first item isdisplayed using a first graphical characteristic, and the second item isdisplayed using a second graphical characteristic. Each item correspondsto a zone and is selectable to cause the corresponding zone to be addedto a zone group. The example configuration of the playback devices inthe playback system includes the zone group. The example processor isconfigured to trigger, based on a selection of the second item via theuser interface, a joining of a second zone corresponding to the seconditem with a first zone group including a first zone represented by thefirst item. The example processor is configured to transmit an updatedconfiguration to at least one playback device in the playback system,the updated configuration based on the joining of the second zone to thefirst zone group.

Some embodiments provide a tangible computer readable storage mediumincluding instruction which, when executed by a computing device, causethe computing device to implement a method. The example method includesaffecting, via the computing device, display and control of a userinterface configured for a display of a wearable device. The exampleuser interface forms a control interface to affect a configuration ofplayback devices in a playback system, and each playback device in theplayback system associated with at least one zone. The example controlinterface is arranged to display at least a first item and a seconditem. The first item is displayed using a first graphicalcharacteristic, and the second item is displayed using a secondgraphical characteristic. Each item corresponds to a zone and isselectable to cause the corresponding zone to be added to a zone group.The example configuration of the playback devices in the playback systemincludes the zone group. The example method includes triggering, via thecomputing device based on a selection of the second item via the userinterface, a joining of a second zone corresponding to the second itemwith a first zone group including a first zone represented by the firstitem. The example method includes transmitting, via the computingdevice, an updated configuration to at least one playback device in theplayback system, the updated configuration based on the joining of thesecond zone to the first zone group.

Some embodiments provide an example method which includes affecting, viathe computing device, display and control of a user interface configuredfor a display of a wearable device. The example user interface forms acontrol interface to affect a configuration of playback devices in aplayback system, and each playback device in the playback systemassociated with at least one zone. The example control interface isarranged to display at least a first item and a second item. The firstitem is displayed using a first graphical characteristic, and the seconditem is displayed using a second graphical characteristic. Each itemcorresponds to a zone and is selectable to cause the corresponding zoneto be added to a zone group. The example configuration of the playbackdevices in the playback system includes the zone group. The examplemethod includes triggering, via the computing device based on aselection of the second item via the user interface, a joining of asecond zone corresponding to the second item with a first zone groupincluding a first zone represented by the first item. The example methodincludes transmitting, via the computing device, an updatedconfiguration to at least one playback device in the playback system,the updated configuration based on the joining of the second zone to thefirst zone group.

In certain embodiments, a graphical characteristic can include a color,a shading, and/or a pattern, etc.

It will be understood by one of ordinary skill in the art that thisdisclosure includes numerous other embodiments. While some examplesdescribed herein may refer to functions performed by one or more givenactors such as “users” and/or other entities, it should be understoodthat this is for purposes of explanation only. The claims should not beinterpreted to require action by any such example actor unlessexplicitly required by the language of the claims themselves.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 inwhich one or more embodiments disclosed herein may be practiced orimplemented. The media playback system 100 as shown is associated withan example home environment having several rooms and spaces, such as forexample, a master bedroom, an office, a dining room, and a living room.As shown in the example of FIG. 1, the media playback system 100includes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130.

Further discussions relating to the different components of the examplemedia playback system 100 and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100, technologies described herein are not limitedto applications within, among other things, the home environment asshown in FIG. 1. For instance, the technologies described herein may beuseful in environments where multi-zone audio may be desired, such as acommercial setting like a restaurant, mall or airport, a vehicle like asports utility vehicle (SUV), bus or car, a ship or boat, an airplane,and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100 of FIG. 1. The playback device200 may include a processor 202, software components 204, memory 206,audio processing components 208, audio amplifier(s) 210, speaker(s) 212,and a network interface 214 including wireless interface(s) 216 andwired interface(s) 218. In one case, the playback device 200 may notinclude the speaker(s) 212, but rather a speaker interface forconnecting the playback device 200 to external speakers. In anothercase, the playback device 200 may include neither the speaker(s) 212 northe audio amplifier(s) 210, but rather an audio interface for connectingthe playback device 200 to an external audio amplifier or audio-visualreceiver.

In one example, the processor 202 may be a clock-driven computingcomponent configured to process input data according to instructionsstored in the memory 206. The memory 206 may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor 202. For instance, the memory 206 may be data storage thatcan be loaded with one or more of the software components 204 executableby the processor 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other embodiments are also possible.

The audio processing components 208 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor (DSP), and soon. In one embodiment, one or more of the audio processing components208 may be a subcomponent of the processor 202. In one example, audiocontent may be processed and/or intentionally altered by the audioprocessing components 208 to produce audio signals. The produced audiosignals may then be provided to the audio amplifier(s) 210 foramplification and playback through speaker(s) 212. Particularly, theaudio amplifier(s) 210 may include devices configured to amplify audiosignals to a level for driving one or more of the speakers 212. Thespeaker(s) 212 may include an individual transducer (e.g., a “driver”)or a complete speaker system involving an enclosure with one or moredrivers. A particular driver of the speaker(s) 212 may include, forexample, a subwoofer (e.g., for low frequencies), a mid-range driver(e.g., for middle frequencies), and/or a tweeter (e.g., for highfrequencies). In some cases, each transducer in the one or more speakers212 may be driven by an individual corresponding audio amplifier of theaudio amplifier(s) 210. In addition to producing analog signals forplayback by the playback device 200, the audio processing components 208may be configured to process audio content to be sent to one or moreother playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. In one example, the audio content andother signals transmitted and received by the playback device 200 may betransmitted in the form of digital packet data containing an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 214 may be configured to parse thedigital packet data such that the data destined for the playback device200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), controldevice(s)within a data network the playback device 200 is associatedwith) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac,802.15, 4G mobile communication standard, and so on). The wiredinterface(s) 218 may provide network interface functions for theplayback device 200 to communicate over a wired connection with otherdevices in accordance with a communication protocol (e.g., IEEE 802.3).While the network interface 214 shown in FIG. 2 includes both wirelessinterface(s) 216 and wired interface(s) 218, the network interface 214may in some embodiments include only wireless interface(s) or only wiredinterface(s).

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”) may further playaudio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc., presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it is understood that aplayback device is not limited to the example illustrated in FIG. 2 orto the SONOS product offerings. For example, a playback device mayinclude a wired or wireless headphone. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100 may be established withone or more playback zones, after which one or more zones maybe added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100 may be dynamically modified, and in some embodiments, the mediaplayback system 100 supports numerous configurations. For instance, if auser physically moves one or more playback devices to or from a zone,the media playback system 100 may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already a playback zone, a new playback zone may be created for theparticular area.

Further, different playback zones of the media playback system 100 maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the dining room zone and the kitchen zone114 may be combined into a zone group for a dinner party such thatplayback devices 112 and 114 may render audio content in synchrony. Onthe other hand, the living room zone may be split into a television zoneincluding playback device 104, and a listening zone including playbackdevices 106, 108, and 110, if the user wishes to listen to music in theliving room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100. As shown, the control device 300may include a processor 302, memory 304, a network interface 306, and auser interface 308. In one example, the control device 300 may be adedicated controller for the media playback system 100. In anotherexample, the control device 300 may be a network device on which mediaplayback system controller application software may be installed, suchas for example, an iPhone™, iPad™ or any other smart phone, tablet ornetwork device (e.g., a networked computer such as a PC or Mac™)

The processor 302 may be configured to perform functions relevant tofacilitating user access, control, and configuration of the mediaplayback system 100. The memory 304 may be configured to storeinstructions executable by the processor 302 to perform those functions.The memory 304 may also be configured to store the media playback systemcontroller application software and other data associated with the mediaplayback system 100 and the user.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 4G mobile communication standard, and so on). Thenetwork interface 306 may enable the control device 300 to communicatewith other devices in the media playback system 100. In one example,data and information (e.g., such as a state variable) may becommunicated between control device 300 and other devices via thenetwork interface 306. For instance, playback zone and zone groupconfigurations in the media playback system 100 may be received by thecontrol device 300 from a playback device or another network device, ortransmitted by the control device 300 to another playback device ornetwork device via the network interface 306. In some cases, the othernetwork device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100 may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100, byproviding a controller interface such as the controller interface 400shown in FIG. 4. The controller interface 400 includes a playbackcontrol region 410, a playback zone region 420, a playback status region430, a playback queue region 440, and an audio content sources region450. The user interface 400 as shown is just one example of a userinterface that may be provided on a network device such as the controldevice 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1)and accessed by users to control a media playback system such as themedia playback system 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100. In some embodiments, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100 of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some embodiments, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100 of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

The above discussions relating to playback devices, controller devices,playback zone configurations, and media content sources provide onlysome examples of operating environments within which functions andmethods described below may be implemented. Other operating environmentsand configurations of media playback systems, playback devices, andnetwork devices not explicitly described herein may also be applicableand suitable for implementation of the functions and methods.

III. Example Playback Device Control Via a Wearable Device

Controller devices and associated controller interfaces help facilitateconfiguration and/or operation of one or more playback devices in amedia playback system. Existing controller interfaces for room grouping,for example, allow users to select rooms and/or zones to perform anaction with respect to the selected rooms/zones (e.g., group the zones,save the grouping, cancel the grouping to leave existing group(s)unchanged). However, as a size of a controller interface shrinks (e.g.,to execute on a smart watch and/or other wearable device), managingcontrol (e.g., room grouping, etc.) via a limited display area becomesmore and more challenging. Certain embodiments disclosed and describedherein provide zone (e.g., room and/or other division, etc.) managementfor a multi-zone system in which a primary and/or secondary controllerapplication has limited available display area. Limited display area(‘display area’ may also be referred to as screen ‘real estate’) resultsin a reduction in information that can be conveyed and a decrease incontrol options that can be provided through the controller interface.

For example, the limited screen real estate of a wearable device, suchas a smart watch, etc., may preclude a controller interface applicationrunning on the wearable device from providing a normal or full set offunctionality. The controller interface may not have space available todisplay both ‘cancel’ and ‘back’ options, for example, when displaying agrouping screen via the controller interface on the wearable device.

In certain examples, a wearable device such as a smart watch (e.g., anApple smart watch, Moto smart watch, LG smart watch, Android Wear smartwatch, Pebble smart watch, Kairos hybrid watch, etc.) may be configuredto run a first controller application which communicates with a secondcontroller application (e.g., a small, faceless application running inthe background, a part or extension of a regular controller applicationrunning and visible for interaction on the controller device, etc.) on acontroller device (e.g., a smart phone, tablet, laptop, desktopcomputer, etc.). For example, the second controller application can be aseparate, standalone controller application, a subordinate controllerapplication for the wearable device, and/or an extension of a regularplayback system controller application running on the controller device,etc. The second controller application communicates with a mediaplayback system (e.g., a Sonos™ playback system). In some examples,rather than updating and displaying a graphical user interfaceassociated with the second controller application, updated userinterface information is provided via the first controller applicationon the wearable device (e.g., the smart watch). The second controllerapplication may relay the updated interface information to the firstcontroller application, for example.

Information such as a current room group, connected household, etc., canbe maintained, updated, and provided from a playback device to the firstcontroller application (via the second controller application). In someexamples, information displayed via an interface associated with thesecond controller application is also provided via an interfaceassociated with the first controller application. In some examples, achange made on the first controller application results in acorresponding change on the second controller application, and viceversa. For example, changing a room on the second controller applicationalso changes the room information on the first controller application,and vice versa.

FIGS. 5A and 5B show example control interfaces 500, 510 designed for aninterface running on a wearable device and/or other mobile deviceconfigured to control a media playback system. In the example interface500 of FIG. 5A, a plurality of icons represent additional interfacescreens, views, and/or functions such as “Edit” 502, “Group All” 504,and “Pause All” 506. Selecting one of the icons 502, 504, 506 triggersan associated function and/or interface screen to execute an actionassociated with the selected icon 502, 504, 506 (e.g., to edit a set ofitems and/or zones, to group all of a set of items and/or zones, topause all of a set of items and/or zones, etc.).

In the example interface 510 of FIG. 5B, a plurality of icons representadditional interface screens, views, and/or functions such as“Favorites” 512, “Rooms” 514, and “Volume” 516. Selecting Favorites 512,for example, brings up an interface showing a list of favorites for aparticular user, wearable device, playback device, playback system, etc.Selecting Rooms 514, for example, displays one or more rooms and/orzones available via a device running the interface 510. Selecting Volume516, for example, facilitates adjustment of a volume or sound levelassociated with one or more rooms/zones accessible via the interface510.

In certain examples, a home or default interface provides a plurality ofselectable options including interfaces 500, 510. Selection of arepresentation associated with the interface 500, 510 transitions thedisplay and control context to that of the respective interface 500,510. In some examples a movement (e.g., shaking, tapping, etc.) of thedevice on which the interface is displayed can trigger a movement to orbetween interfaces 500, 510. In another example, a swipe (e.g., ahorizontal movement, vertical movement, and/or other movement across adisplay screen showing the interface) triggers a change from interface500 to 510 and vice versa.

In certain examples, a first controller application on a controllerdevice is interacting with a second controller application on a wearabledevice. The wearable device (e.g., a smart watch, smart band, etc.)includes an organic light-emitting diode (OLED) or othersemi-transparent layer for electronic content display. By default, theinterface 500 or 510 is hidden or not displayed on the wearable device.The interface 500 or 510 can be activated for display on the wearabledevice based on: 1) manual user action (e.g., a button press, swipe,particular arm movement/gesture, etc.); 2) a change in configuration(e.g., a change in controller configuration, a change in zone groupconfiguration, a change to/from ‘party mode’, other change in playbacksystem setting, etc.); 3) an approaching playback event (e.g., an end tothe user's playlist, an end to a zone's play queue, an alarm, etc.).Thus, an interaction between the wearable device, controller device,playback system, and/or trigger event determines whether the wearabledevice controller interface is displayed, made available forinteraction, updated, etc., on a wearable device in which the defaultmode is one of hidden operation unless an alert is to be generated or aprompt for a next action is triggered.

In certain examples, selecting an interface option such as Edit 502,Rooms 514, etc., triggers display of a room/zone edit and/or groupinginterface. FIG. 5C depicts one such example interface 520. In someexamples, a controller interface can display a “Now Playing” view,allowing selection of one or more multimedia content items for playbackas well as volume control, etc. Within the Now Playing menu and/or as aselectable option, an “Edit” menu displays and facilitates selection ofone or more zones, rooms, and/or players to control grouping of theselected zones/rooms/players. For example, when a controller interfaceis in a room group context or mode (such as a Now Playing menu context),an edit mode can be triggered for the group which transitions theinterface to a grouping interface such as the example edit mode of FIG.5C. After a grouping has been completed, control can transition back tothe previous (e.g., Now Playing, etc.) interface mode and associateddisplay.

In the example of FIG. 5C, the interface 520 shows three ungrouped zonesthat may be selected for zone grouping: “Backstage” 522, “Dance Floor”524, and “Living Room” 526. One or more of the zones 522, 524, 526 canbe selected to trigger a grouping with one or more other zones 522, 524,526. In certain examples, a coloring, shading, pattern, and/or othergraphical characteristic associated with the zone name and/or iconchanges based on whether the zone is grouped with another zone, to whichother zone the zone is grouped, an ungrouped status of the zone, etc.

For example, as illustrated in FIG. 5C, zones are represented in a listof selection items: Backstage 522, Dance Floor 524, and Living Room 526.Each item 522, 524, 526 can be selected to trigger a zone grouping modeto group one or more zones corresponding to items 522, 524, 526,respectively, into a new or existing zone group.

FIG. 6A shows an example interface 600 in which a representation of a“Backstage” zone 610 is selected for grouping. The example of FIG. 6Ashows an initial screen for grouping zones/players/rooms starting with“Backstage” 610. Each zone 610, 620, 630 shown in the example of FIG. 6Aincludes a grouping indicator 612, 622, 632, a zone name 614, 624, 634,and a grouping trigger 616, 626, 636. A “Done” button or link 640 exitsa group edit mode and confirms the updated group configuration, forexample.

In FIG. 6A, the grouping indicator for “Backstage” 612 is depicted in adifferent color (e.g., shown in the example of FIG. 6A as filled in forpurposes of example illustration only) than the grouping indicators for“Dance Floor” 622 and “Living Room” 632 (e.g., shown in white or clearfor purposes of example illustration only). In the example of FIG. 6B,the representation of Dance Floor 620 has been selected along with therepresentation of Backstage 610. For example, the grouping trigger 626for Dance Floor has been selected (e.g., clicked on, hovered over,and/or otherwise activated), and, as a result, the grouping indicator622 for Dance Floor changes to match the grouping indicator 612 forBackstage.

As shown in FIG. 6C, Backstage and Dance Floor are grouped. Theresulting group 650 includes a group name 652, names of the group'sconstituent zones 614, 624, and a grouping indicator 654. Living Room630 is represented as a separate zone because it has not been groupedwith Backstage 610 and Dance Floor 620. Representations 610, 620 (andtheir associated zones) can be grouped upon an indication of completion(e.g., selection of “Done” 640 via the interface 600) and/or dynamicallyas selections are being made, for example). In some examples, a changein grouping is formalized upon acknowledgement from one or more playbackdevices in the affected zones. In other examples, a change in groupingis reflected dynamically without waiting for confirmation oracknowledgement. Thus, representations (e.g., names, icons, etc.) ofzones, players, rooms, etc., can be selected in a grouping mode totrigger a grouping of the selected zones/players/rooms/etc. Asillustrated in the example of FIG. 6C, a grouping 650 of Backstage 614and Dance Floor 624 is displayed for control and/or other interaction.Living Room 634 is displayed individually for control and/or otherinteraction via the example interface 600.

FIG. 7 shows an example control system 700 for a media playback network.The example system 700 includes a wearable device 710 and controllerdevice 720. The controller device 720 (e.g., a tablet computer, smartphone, laptop computer, desktop computer, television, etc.) communicateswith the wearable device 710 (e.g., a smart watch, a smart band, etc.)and interfaces with a playback system 730 (e.g., a media playbacksystem) to facilitate control (e.g., configuration, playback of content,etc.) of the playback system 730 and its constituent zones 740, 742,744, 746, 748. As shown in the example of FIG. 7, zones can be organizedinto zone groups, such as zone group 750 including zones 746 and 748.

In the example system 700, the wearable device 710 includes a firstcontroller application 715 which facilitates display of a controlinterface on the wearable device 710 as well as communication with thecontroller device to display, for example, available zones 740-748, zonegroup(s) 750, currently playing content, content available for playback,configuration options (e.g., group, ungroup, etc.), playback options(e.g., play, pause, volume, etc.), etc.

In the example system 700, the controller device 720 includes a secondcontroller application 725 which communicates with the first controllerapplication 715 of the wearable device 710 to facilitate control of theplayback system 730 as well as facilitate display of information andcontrol via the controller device 720. For example, the secondcontroller application 725 can facilitate display, via the controllerdevice 720, of available zones 740-748, zone group(s) 750, currentlyplaying content, content available for playback, configuration options(e.g., group, ungroup, etc.), playback options (e.g., play, pause,volume, etc.), etc. The second controller application 725 can also relayconfiguration and/or other control information from the first controllerapplication 715 to one or more components of the playback system 730(e.g., zone grouping, ungrouping, play, pause, volume and/or otherequalization setting, etc.).

In operation, the controller device 720 communicates with the wearabledevice 710 and one or more components of the playback system 730 tofacilitate playback of media content and/or configuration of the firstcontroller application 715, zone(s) 740-748, zone group 750, etc. Thesecond controller application 725 on the controller device 720 interactswith the first controller application 715 on the wearable device 710 toupdate display of playback system 730 information and available controloptions and receive commands and/or other input from the firstcontroller application 715 on the wearable device 710.

Alternatively or in addition, for example, the first controllerapplication 715 retrieves zone 740-748 and zone group 750 configurationinformation via the second controller application 725 (which may obtainthe information via a configuration update from the playback system 730,for example) and graphically displays the configuration information viaa screen on the wearable device 710. In other examples, configurationupdates can be pushed (e.g., periodically, based on an event (e.g., achange in playback system 730 configuration) and/or other trigger, etc.)to the first controller application 715 by the second controllerapplication 725 and/or the playback system 730 without a request fromthe first controller application 715.

The first controller application 715 facilitates zone grouping,ungrouping, playback control, etc., based on a selection at the wearabledevice 710 passed to the controller device 720 to trigger a change inthe playback system 730. In certain examples, the first controllerapplication 715 displays individual zones 740, 742, 744 in a firstcolor, shading, pattern, and/or other graphical characteristic distinctfrom a second color, shading, pattern, and/or other graphicalcharacteristic used to display the zone group 750 and its member zones746, 748. As zones 740-748 are moved in and out of the zone group 750,used to form a second zone group (not shown), etc., acoloring/shading/pattern/etc. of the representations of the zone(s)and/or zone group(s) on a user interface associated with the firstcontroller application 715 (and also the second controller application725) is automatically adjusted by the first controller application 715operating in conjunction with the second controller application 725 andcommunicating with the playback system 730.

For example, a screen of the wearable device 710 (e.g., smart watch,smart band, etc.) shows a list of selectable items. Each item is agraphical or other visual representation of a zone 740-748 (e.g., aroom, media playback device, medical playback zone, etc.). Each item canbe selected via the interface on the wearable device 710 to join and/orremove the zone 740-748 corresponding to the selected item from a groupof zones (e.g., zone group 750). In certain examples, a zone is shown ina “grouping color” (and/or other such shading, pattern, and/or othervisual indication) that visually indicates that the first controllerapplication 715 is in a grouping mode and any other zone that is thenselected while in the grouping mode will be grouped with the given zone.Upon such a grouping, the given zone and the selected zone are shown inthe same color, shade, pattern, and/or other graphical characteristic,etc. Thus, items representing zones that are already grouped togetherare displayed in the same color and other items apart from the group aredisplayed in different color(s) to visually distinguish between zones,zone groups, and/or modes of operation, for example.

In some examples, a selection area (e.g., a box, circle, oval, otherborder, etc.) (e.g., the box shown in FIG. 6C, etc.) shares a color withitem(s) representing zones that were already a member of the zone groupbefore the edit screen is displayed. When an item is selected, thatitem's color may remain unchanged until the grouping is completed (e.g.,the second controller application 725 notifies the sub-controllerapplication 715 that the playback system 730 zones have received andimplemented the grouping notification, trigger, instruction, etc. (e.g.,update of a grouping state table, network topology, network/groupingstate variable, etc.).

In some examples, item coloration can be updated before the updatedconfiguration is sent to the playback system 730. In other examples, achange in item coloration occurs after the configuration has been sentto the playback system 730 and a response has been receivedacknowledging the change (e.g., providing an updated configurationand/or other confirmation message, etc.).

In certain examples, the first controller application 715 (and secondcontroller application 725) can include an edit, edit rooms, edit zones,etc., dialogue as part of a controller interface executing on thewearable device 710. The “edit” type dialogue can include a group orgrouping dialogue that lists or otherwise shows zones/rooms/playbackdevices available for grouping. For example, upon selection of a givenzone (which, for example, can be labeled and/or designated as a groupcoordinator), the “grouping” dialogue is launched with the given zonebeing the lead zone (e.g., presented in a different color, shade,pattern, other graphical characteristic, etc.) of the “grouping”dialogue.

Referring back to the example of FIG. 6A, the interface 600 displays agrouping dialogue driving by a first controller application 715, and theBackstage zone 610 has been selected for editing of an associated group.In the grouping dialogue, Backstage 610 is represented in a color 612different from the other zones 622, 632. However, as illustrated in theexample of FIG. 6B, as other zones (e.g., Dance Floor 620) are selectedto become part of a group with Backstage 610, a corresponding colorindication 622 is provided for each of those zones 620 to become part ofthat group. One or more zones can be selected to join a group, can bedeselected to remove from a group, etc., and coloring of the zonerepresentations will be automatically be adjusted by the firstcontroller application 715 to reflect the change in grouping status inthe grouping mode.

In an example, a first user has a smart watch running a first controllerapplication for a Sonos™ playback network. A second user has a secondcontroller application running on a smart phone for the same Sonos™playback network. If the second user adds a living room zone to thebackstage group, the second controller application informs the firstcontroller application of the update. As a result of the update, arepresentation of the living room zone may turn a particular color, suchas blue, along with the backstage representation since the zones are nowgrouped together.

In some examples, the wearable device 710 (e.g., a smart watch) includesa “glance” screen which provides a snapshot of the playback network 730and/or device 710 status. For example, the glance screen provides a“quick” view of the controller application's content, such as media nowplaying, playback network configuration, etc. In some examples, theglance screen updates dynamically accordingly to a currently playingzone and/or zone group on the tethered second controller application725. Selection of all or part of the glance screen can be used to open alarger, more detailed view of the controller application or portionthereof.

In certain examples, interaction with a screen and/or other surface ofthe wearable device 710 triggers a change in context or mode via thefirst controller application 715 (e.g., transitioning from a status or“at a glance” mode to an editing mode based on a swipe of the watchscreen, etc.). An example wearable device 710 includes a touch screen todisplay a user interface associated with the first controllerapplication 715. As illustrated in the example of FIG. 8, the firstcontroller application 715 can include and/or work in conjunction with auser interface communicator 802, a swipe detector 804, an analyzer 806,a current context tracker 808, a context changer 810, and one or morecontrol context definitions 812.

Generally, the example first controller application 715 of FIG. 8enables a user of a touch screen interface to quickly and efficientlychange between control contexts of the wearable device 710 and itsassociated controller device 720 (executing the second controllerapplication 725). That is, the example first controller application 715enables the user of the touch screen interface to quickly andefficiently change which mode and associated functions are provided forinteraction via the wearable device 710 interface (and the associatedcontroller device 720 interface).

Using a single touch and/or swipe of a finger and/or other skin acrossthe touch surface of the wearable device 710, the first controllerapplication 715 transitions among a plurality of screens, menus, modes,and/or other options such as from a time view to a now playing view to agrouping view, etc. As described above, the wearable device 710 and itsfirst controller application 715 can transition from the exampleinterface 500 of FIG. 5A to the example interface 510 of FIG. 5B using atouch and/or swipe motion on the touch surface of the wearable device710. Thus, rather than navigating through multiple screens and multipleselections, a swipe, touch, and/or other skin movement alters a controlcontext of the first controller application 715 (and associated secondcontroller application 725). In certain examples, available controlcontexts (e.g., interface screens, menus, modes, and/or other options,etc.) can be cycled through in a particular order (e.g., time followedby play queue followed by editing, etc.) such as a circular list ofcontext options. In certain examples, touch-sensitive context switchingoccurs in response to touch only in a certain area of the wearabledevice 710.

The example first controller application 715 of FIG. 8 includes a userinterface communicator 802. The user interface communicator 802interacts with or may be integrated with a user interface of thewearable device 710. The user interface communicator 802 enables thefirst controller application 715 to receive information regarding inputvia the user interface of the wearable device 710. Additionally oralternatively, the user interface communicator 802 designates a portionof a display to be presented on a user interface screen of the wearabledevice 710 that is to be associated with the first controllerapplication 715. In the illustrated example, the user interfacecommunicator 802 designates a status section (e.g., Now Playing,Playlist, Edit, Groups, Favorites, etc.) of a user interface implementedby the first controller application 715 for an input that changes thecontrol context of the first controller application 715.

For example, the Now Playing status includes information related to amedia presentation (e.g., output of an audio track) being presented in aparticular zone of, for example, the system 100 of FIG. 1. That is, theNow Playing status describes (e.g., via information related to metadata)media that is playing in a zone (e.g., the living room of the system 100of FIG. 1). A name of the current zone is displayed in the Now Playingsection of the wearable device 710 interface (e.g., in a certain color).The Grouping status includes information related to available zone(s),current zone group(s), etc., as well as option(s) to adjust zonegrouping(s), for example.

The user interface communicator 802 receives information related tointeractions between a user and the displayed user interface andprovides the received information to a swipe detector 804. The swipedetector 804 interprets information received via the user interfacecommunicator 802 to determine whether the user has swiped the touchscreen. Such an input is understood by the user to change controlcontexts of the first controller application 715 (and associated secondcontroller application 725). As described above, a control contextrefers to a mode of the first controller application 715 indicative ofwhich option(s), state, menu, etc., are available for interaction viathe user interface. When a user wants to, for example, configure a zonegroup, the user performs a swiping motion on a surface of the wearabledevice 710 to enter the first controller application 715 into a controlcontext associated with zone grouping/editing to configure one or morezone groups. The swipe detector 804 is capable of detecting such a swipeand in which direction (e.g., right or left) the swipe occurred.

When the swipe detector 804 determines that a swipe has occurred (e.g.,based on information received via the user interface communicator 802),the swipe detector 804 informs an analyzer 806 that a swipe has occurredand provides a direction of the swipe to the analyzer 806. The exampleanalyzer 806 determines which control context the first controllerapplication 715 was in prior to the detected swipe by referencing acurrent context tracker 808. The current context tracker 808 may be amemory location that indicates which control context the firstcontroller application 715 is in. The example current context tracker808 includes an identifier of in which mode, menu, set of options, etc.(e.g., now playing, rooms, edit, favorites, etc.), the first controllerapplication 715 is currently operating. However, the informationdefining each control context is stored in a control context definitionsdatabase 812. The example database 812 also includes an order in whichthe control contexts are to be displayed on the user interface of thefirst controller application 715. This order may be stored as a list inthe database 812.

The analyzer 806 uses the information from the current context tracker808, the direction of the swipe, and the list of the database 812 todetermine in which control context the detected swipe placed the firstcontroller application 715. For example, when the current controlcontext is the Now Playing context that is first in the list, the swipedetector 804 detects a leftwards swipe in the Now Playing section, andthe Edit Zones context is second in the list, the analyzer 806determines that the first controller application 715 is to change fromthe Now Playing context to the Edit Zones context. Such a change altersthe first controller application 715 (and associated second controllerapplication 725) to control the grouping and/or ungrouping of physicaldevices associated with available zones (e.g., the zone player 124 ofFIG. 1). As a result, selectable icons and/or other options forgrouping/ungrouping are displayed (e.g., shown in one or morecolorizations, patterns, representations, etc.) for configuration andcontrol via the first controller application 715 (and associated secondcontroller application 725), for example.

When the analyzer 806 determines that such a change in control contextsoccurred, a context changer 810 changes the control context of the firstcontroller application 715 (and/or associated second controllerapplication 725). For example, the context changer 810 alters whichcontext identifier is stored in the current context tracker 808.Additionally, the context changer 810 cooperates with the user interfacecommunicator 802 to reflect the newly entered control context.

Thus, certain examples facilitate grouping, ungrouping, and/or othermanagement of zones using reduced or “little” screen real estateavailable on a wearable device. Certain examples facilitate interactionbetween a feature-reduced controller application running on a wearabledevice and a more complete or “full” controller application running on acontroller device, which serves as an intermediary to provide command,control, configuration, etc., to one or more components of a playbacksystem. In certain examples, color-coding and/or other visualdistinction working in combination with shifting interface screens andcontrol modes for group edit, etc., allows a wearable device havinglimited available screen real estate to affect configuration and controlof zones in a playback system or network.

Certain examples provide a hierarchy or family of user interfacesdesigned for a variety of different devices. For example, a compact ormicro-interface can be provided for small, wearable devices (e.g., watchfaces, bands, etc.). A standard interface can be provided for othercontroller devices such as smart phones and tablets. A larger interfacecan be provided for desktop and laptop computers. A macro interface canbe provided for televisions, projection screens, etc. Some or allelements of the control interfaces disclosed and described herein can beapplied to other interfaces beyond the micro interface, although many ofthe described features are particularly beneficial in solving problemspresented by the limited display area available for a micro interface ona wearable device.

FIG. 9 illustrates an example data flow diagram 900 depicting a flow ofdata between the wearable device 710 (and its associated firstcontroller application 715), controller device 720 (and its associatedsecond controller application 725), and playback system 730 (andassociated zones 740-748). As shown in the example of FIG. 9, a zoneconfiguration 915 is transmitted from the second controller application725 to the zones 740-748 of the playback system 730. The zoneconfiguration 915 can include zone names, zone grouping identification,zone and/or zone group representation parameter(s) (e.g., color,pattern, etc.), currently playing content, other state variable(s), etc.One or more zones 740-748 provide an acknowledgement 920 back to thecontroller device 720.

The second controller application 725 then passes the zone configuration925 on to the first controller application 715 running on the wearabledevice 710. The wearable device 710 and its first controller application715 update an associated graphical user interface using on the zoneconfiguration 925.

Based on interaction with the first controller application 715 on thewearable device 710, a change in mode 930 is triggered (e.g., based onuser selection, swipe, etc., via the user interface associated with thefirst controller application 715 on the wearable device 710) andprovided by the first controller application and wearable device 710 tothe second controller application 725 running on the controller device720, which provides an acknowledgement 935 back to the first controllerapplication 715 on the wearable device 710. For example, a change from a‘Now Playing’ mode to an ‘Edit Zones’ mode is triggered on the wearabledevice 710 and notification of the change in mode/context is sent to thesecond controller application 725 on the controller device 720.

With the wearable device 710 in its changed mode (e.g., in an Edit Zonesmode), a change in zone configuration is facilitated via the firstcontroller application 715. For example, the user can manipulate a zonegrouping via the graphical user interface associated with the firstcontroller application 715 on the wearable device 710. As a result ofthe input obtained via the wearable device 710 (e.g., the watch), thewearable device 710 provides the configuration change 940 (e.g., updatedzone grouping information, associated change in zone representation(e.g., color, pattern, shading, etc., of zones in a group) on theinterface corresponding to grouping, etc.) to the second controllerapplication 725 running on the controller device 720. The secondcontroller application 725 on the controller device 720 relays theconfiguration change 945 to one or more devices (e.g., one or more zones740-748) in the playback system 730. One or more zones 740-748 receivingthe change in zone configuration 945 from the first controllerapplication 715 via the second controller application 725 can adjust oneor more configuration parameters, zone relationship(s), state table,network topology, zone group variable(s), etc., to reflect the updatedconfiguration.

Thus, in certain examples, a third device (e.g., the wearable device710) acts as a control device for the playback system 730 but does notcommunicate directly with a playback device or zone 740-748 in theplayback system 730. Instead, the first controller application 715running on the wearable device 710 relies on a second controllerapplication 725 running on a controller device 720 to communicate withplayback devices on the playback network 730. While the secondcontroller application 725 may be able to accept control inputs via agraphical user interface running on the controller device 720, in such aconfiguration the second controller application 725 receives controlinputs from the tethered wearable device 710 and its first controllerapplication 715. In some examples, a cover or “glance” screen displayedby the first controller application 715 on the wearable device 710updates dynamically according to a currently playing zone and/or zonegroup on the tethered second controller application 725.

In certain examples, the wearable device 710 is paired with or tetheredto the controller device 720 through an exchange of messages between thefirst controller application 715 and the second controller application725. The first and second controller applications 715, 725 exchangemessages (e.g., automatically and/or on command) to identify themselvesand establish a relationship between the applications 715, 725 forexchange of commands, status, and configuration information, forexample. In some examples, multiple wearable devices 710 can be pairedwith a single controller device 720. Alternatively or in addition,multiple controller devices 720 can be paired with a single wearabledevice 710. In some such examples in which multiple devices are pairedwith or tethered to a single device, one device may be designated as amaster and/or message timing can be considered to avoid multiple devicesrelaying the same message to another device and/or to the playbacksystem 730. State variables (and changes therein) can also be used toavoid unintentional errors resulting from duplicate commands, forexample.

For example, when the first controller application 715 is launched onthe wearable device 710, the first controller application 715 retrievesstate variable(s) for the playback system 730 (e.g., via the secondcontroller application 725) and displays information based on theretrieved state variable(s). When an instruction for a change inconfiguration is sent from the first controller application 715 on thewearable device 710, the wearable device 710 sends a message to thecontroller device 720 when then sends a message to the playback system730 to make the change. The playback system 730 confirms or otherwiseacknowledges the change in a message or change in state variable to thecontroller device 720, which can cause the wearable device 710 toupdate, for example.

FIG. 10 shows a flow diagram that illustrates an example method 1000 tofacilitate zone grouping and control in a playback system (e.g.,playback system 730). In certain examples, a computing device (e.g.,controller device 720) and a processor execute the example method 1000.The computing device includes a communication interface configured toexchange data and commands between the computing device and a wearabledevice (e.g., wearable device 710) to control the playback system. Theprocessor is configured to receive and process input in conjunction withthe communication interface to facilitate control of the playback systemat least by executing the example method 1000.

At block 1002, display and control of a user interface configured for adisplay of the wearable device are affected by the computing device. Forexample, the user interface forms a control interface to affect aconfiguration of playback devices in the playback system, and eachplayback device in the playback system is associated with at least onezone. In the example of FIG. 10, the control interface is arranged todisplay at least a first selectable item and a second selectable item,each item corresponding to a zone and selectable to cause thecorresponding zone to be one of added to or removed from a zone group.The example zone group forms part of the configuration of the playbackdevices in the playback system. For example, a Backstage label and aDance Floor label are displayed as the first and second selectable itemsvia the user interface on a smart watch.

At block 1004, based on a selection of the second item via the userinterface, a joining of a second zone corresponding to the second itemwith a selected first zone group is triggered. The first zone groupincludes a first zone represented by the first item, for example. In theexample of FIG. 10, the first item is displayed in a first color and thesecond item representing the second zone is displayed in a second color.For example, selection of the Dance Floor label triggers a grouping ofthe Dance Floor zone with the Backstage zone. In certain examples, priorto the selection of the second item, a plurality of mode options aredisplayed, and a selection of an edit mode is received from theplurality of mode options.

At block 1006, a graphical representation of the second item is updated,based on the joining of the second zone to the first zone group, todisplay the second item in the first color. For example, the Backstagelabel associated with the Backstage zone is displayed in the firstcolor, and the Dance Floor label associated with the Dance Floor zone isinitially displayed in the second color but is changed to display in thefirst color once the Dance Floor zone is grouped with the Backstagezone.

At block 1008, an updated configuration is transmitted to at least oneplayback device in the playback system. The updated configuration isbased on the joining of the second zone to the first zone group, forexample. For example, the updated configuration including the DanceFloor zone grouped with the Backstage zone is transmitted by thecomputing device to one or more zones in the playback system.

FIG. 11 shows a flow diagram that illustrates an example method 1100 tofacilitate zone grouping and control in a playback system (e.g.,playback system 730). In certain examples, a wearable device (e.g.,wearable device 710 executing the first controller application 715)communicates with a computing device (e.g., the controller 720) toexchange data and commands between the wearable device and the computingdevice to control the playback system and execute the example method1100.

At block 1102, a user interface providing information and control via adisplay screen of the wearable device is displayed. The example userinterface forms a control interface to affect a configuration ofplayback devices in the playback system, and each playback device in theplayback system is associated with at least one zone. In the example ofFIG. 11, the control interface is arranged to display at least a firstselectable item and a second selectable item, each item corresponding toa zone and selectable to cause the corresponding zone to be one of addedto or removed from a zone group. The example zone group forms part ofthe configuration of the playback devices in the playback system. Forexample, a Backstage label and a Dance Floor label are displayed as thefirst and second selectable items via the user interface on a smartwatch.

At block 1104, selection of the first item triggers entry into a zonegrouping mode. In certain examples, a plurality of mode options aredisplayed, and a selection of an edit mode is received from theplurality of mode options. For example, selecting the Backstage labeltriggers the wearable device to operate in a zone grouping or edit moderather than a now playing mode.

At block 1106, based on a selection of the second item via the userinterface, a second zone corresponding to the second item is joined withthe selected first item into a first zone group. The first zone groupincludes a first zone represented by the first item, for example. In theexample of FIG. 11, the first item is displayed in a first color and thesecond item representing the second zone is displayed in a second color.For example, selection of the Dance Floor label triggers a grouping ofthe Dance Floor zone with the Backstage zone.

At block 1108, a graphical representation of the second item is updated,based on the joining of the second zone to the first zone group, todisplay the second item in the first color. For example, the Backstagelabel associated with the Backstage zone is displayed in the firstcolor, and the Dance Floor label associated with the Dance Floor zone isinitially displayed in the second color but is changed to display in thefirst color once the Dance Floor zone is grouped with the Backstagezone.

At block 1110, an updated configuration is transmitted to at least oneplayback device in the playback system. The updated configuration isbased on the joining of the second zone to the first zone group, forexample. For example, the updated configuration including the DanceFloor zone grouped with the Backstage zone is transmitted by thecomputing device to one or more zones in the playback system. In certainexamples, the computing device (e.g., the controller) relays the updatedconfiguration from the wearable device to a plurality of playbackdevices corresponding to the plurality of zones in the playback system.

In certain examples, the order of blocks in the FIG. 11 can vary fromthe example order depicted. For example, the update of the graphicalrepresentation of the second item at block 1108 to match the first itemafter the updated configuration has been transmitted to at least oneplayback device at block 1110. In such examples, after anacknowledgement has been received from the playback device regarding theupdated configuration (or the playback device has sent an updatedconfiguration in response to a change instruction from the controller),then the graphical representation of the second item is changed to matchthe graphical representation of the first time (block 1108).

FIG. 12 shows a flow diagram that illustrates an example method 1200 tofacilitate zone grouping and control in a playback system (e.g.,playback system 730). In certain examples, the playback system receivesan updated configuration from a computing device (e.g., controller 720),which communicates with a wearable device (e.g., wearable device 710) tocontrol the playback system and execute the example method 1200.

At block 1204, a zone configuration for zones in the playback system isreceived by one or more zones in the playback system. The configurationcan identify zones in the playback system and specify one or moregroupings of those zones to play certain content in synchrony among theplayback devices in the zone group, perhaps based on a certain trigger(e.g., time, selection, event, etc.). One or more zones (e.g., allzones, a designated “primary” or “master” zone, a zone groupcoordinator, etc.) can store the zone configuration to facilitateoperation of the playback system, for example.

At block 1204, playback of media content via the playback system isfacilitated according to the zone configuration. For example, playbackof audio content (e.g., stored audio files, streaming audio, multimediafiles, etc.) is facilitated via the playback system according to thezones (and associated playback devices) and zone groupings specified inthe zone configuration (e.g., topology, state variable, configurationtable, etc.).

At block 1206, an updated zone configuration is received by one or morezones in the playback system. For example, selection of zones to form azone group via the computing device and/or the wearable device resultsin a change in a zone grouping and, as a result, an update or change inthe zone configuration for the playback system. The computing device canthen send the updated zone configuration to the playback system so thatone or more zones in the playback system stored the updatedconfiguration and operate in accordance with the updated zoneconfiguration information (e.g., new zone grouping, etc.).

At block 1208, playback of content via the playback system isfacilitated according to the updated zone configuration. At block 1210,an update to the playback system can be transmitted back to thecomputing device. For example, addition or removal of a playback deviceto the playback system results in a configuration change that iscommunicated to the computing device. The computing device can propagatethe change to the user interface displayed on the wearable device.Further action via a controller interface can result in furtheradjustment to zone grouping and/or other playback system configurationparameter(s) and/or other setting(s), for example.

FIG. 13 shows a flow diagram that illustrates an example method 1300 tofacilitate zone grouping and control in a playback system (e.g.,playback system 730). In certain examples, a wearable device (e.g.,wearable device 710 executing the first controller application 715)communicates with a computing device (e.g., the controller 720) toexchange data and commands between the wearable device and the computingdevice to control the playback system and execute the example method1300.

At block 1302, control and playback of multimedia content arefacilitated via the playback system. For example, the computing deviceand/or wearable device, working individually and/or together, provideconfiguration information (e.g., a zone configuration, etc.), playbackinstructions, content, and/or other control to affect operation andother behavior of one or more playback devices forming one or more zonesand/or zone groups in the playback system.

At block 1304, a plurality of selectable options are displayed via auser interface display on the wearable device. For example, a firstcontroller application 715 running on the wearable device 710 and drivenby the second controller application 725 running on the controllerdevice 720 generates a user interface display, shown on the wearabledevice 710, which represents a plurality of options (e.g., play, rooms,edit, favorites, etc.) based on name, icon, location, hierarchy, etc.

At block 1306, selection of an option displayed via the user interfaceis received. For example, selection of an option is received at thecomputing device (e.g., the controller 720) and/or received by thewearable device (e.g., wearable device 710) and relayed from thewearable device to the computing device.

At block 1308, based on the selection, entry into an edit mode isdetermined. For example, if the selected option is an edit option (e.g.,edit rooms, edit zones, edit groups, edit, etc.), then an editing modeis triggered (e.g., a zone/zone group edit mode, etc.). In the editmode, the grouping and/or other arrangement of zones can be edited forthe playback system.

At block 1310, a plurality of selected items are displayed via the userinterface. For example, a first controller application 715 running onthe wearable device 710 and driven by the second controller application725 running on the controller device 720 generates the user interfacedisplay, shown on the wearable device 710, which represents a pluralityof zones/zone group(s) for the playback system as selectable items basedon name, icon, location, hierarchy, etc.

At block 1312, selection of a first item displayed via the userinterface is received. For example, selection of a first item isreceived at the computing device (e.g., the controller 720) and/orreceived by the wearable device (e.g., wearable device 710) and relayedfrom the wearable device to the computing device. The selection of thefirst item (e.g., a first item displayed in a first color and/orpattern, etc.) triggers a zone grouping mode for a first zone associatedwith the first item. In the zone grouping mode, the computing deviceand/or wearable device awaits a second item to group with the first itemto form and/or add to a zone group (e.g., form a new zone group is notcurrently in a zone group and add to a first zone group if the firstzone is currently a member of the first zone group, etc.).

At block 1314, selection of a second item displayed via the userinterface is received. For example, selection of a second item isreceived at the computing device (e.g., the controller 720) and/orreceived by the wearable device (e.g., wearable device 710) and relayedfrom the wearable device to the computing device.

At block 1316, the selection of the second item is evaluated todetermine whether the second item (e.g., displayed in a second colorand/or pattern, etc.) is to be added to a zone group. If so, then atblock 1318, a zone group configuration is updated to reflect theaddition of the second zone associated with the second item to the zonegroup, and at block 1320, a representation of the second item is updatedbased on the zone grouping. For example, the second zone is grouped withthe first zone to form a first zone group, and, at block 1320, arepresentation of the second item is transformed or otherwise updated tobe shown in the same first color, pattern, etc., as the first item. Asanother example, the second zone is grouped into an existing first zonegroup with the first zone (and potentially other zones as well), and, atblock 1320, the representation of the second item is transformed orotherwise updated to be shown in the same first color, pattern, etc., asthe first item.

Alternatively, the selected second item can correspond to a second zonethat is already in the first zone group with the first zone. Theselected second item can be removed from the first zone group, resultingin an updated zone configuration and a change in the representation ofthe second item to be a second color/pattern/etc. different from that ofthe first zone, for example.

At block 1322, if the system isn't in an edit mode and/or the selectedsecond item is not to be added to a zone group, then configuration ofthe selected item/option can otherwise be updated based on input,parameters, environment, currently playing content, etc. For example,selection of an item or other option can result in a change in volumefor playback, play/pause playback of media content, selection of newmedia content for playback, designation of content as a “favorite”,selection of a room/zone, and/or other control of playback systemoperation and/or configuration.

At block 1324, the updated configuration is transmitted to thecontroller. For example, the updated configuration can be transmitted tothe controller by a controller application running on the controller.Alternatively or in addition, the updated configuration can betransmitted from the wearable device to the controller. At block 1326,the updated configuration is transmitted from the controller to theplayback system. For example, the controller device transmits theupdated configuration to one or more playback devices (e.g., zones) inthe playback network so that the devices can process the updatedconfiguration and configure themselves for communication, playback,and/or other settings according to the new zone group configuration.

Although the blocks of methods 1000-1300 are illustrated in sequentialorder, these blocks may also be performed in parallel, and/or in adifferent order than those described herein. Also, the various blocksmay be combined into fewer blocks, divided into additional blocks,and/or removed based upon the desired implementation.

In addition, for the methods 1000-1300 and other processes and methodsdisclosed herein, the flowcharts show functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the methods 1000-1300 and other processes and methodsdisclosed herein, each block in FIGS. 10-13 may represent circuitry thatis wired to perform the specific logical functions in the process.

Thus, for example, in operation, a playback device outputs contentaccording to one or more playback settings. Operation for playbackand/or other configuration of the playback device occurs and/or isadjusted in response to a determination of zone grouping and/or othermodification via a controller device and associated wearable device.

IV. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

The example embodiments described herein provide systems and methods tofacilitate zone grouping and adjustment of zone representation dependentupon a zone's grouping status. Certain embodiments enable and/orfacilitate interaction between a wearable or mobile device having afirst controller application, a controller device having a secondcontroller application, and a playback system including one or moreplayback devices organized according to one or more zones that may ormay not be grouped into one or more zone groups. By representing groupedzones in the same way (e.g., same color, same pattern, etc.), a groupedrelationship and confirmation of successful grouping, etc., can bereadily and easily enabled and verified.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of aninvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware. It may be noted that operationsperformed by the computing device and/or other components disclosed anddescribed herein (e.g., operations corresponding to process flows ormethods discussed herein, or aspects thereof) may be sufficientlycomplex that the operations may not be performed by a human being withina reasonable time period.

We claim:
 1. A wearable device, comprising: a user interface; acommunication interface; a processor; a non-transitory computer-readablemedium; and program instructions stored on the non-transitorycomputer-readable medium that, when executed by the processor, cause thewearable device to perform functions comprising: receiving, from acomputing device, respective configuration information corresponding toeach of a plurality of network devices in a household that have beengrouped together, wherein the computing device is configured tofacilitate control of each of the plurality of network devices in thehousehold via a data network, and wherein the plurality of networkdevices includes a first network device; displaying, via the userinterface, an indication of the first network device; receiving, via theuser interface, a first user input indicating a selection of the firstnetwork device; in response to receiving the first user input,displaying, via the user interface, a representation of configurationinformation corresponding to the first network device that is indicativeof a configuration of the first network device; receiving, via the userinterface, a second user input indicating a requested change to theconfiguration of the first network device; in response to receiving thesecond user input, transmitting, via the communication interface to thecomputing device, a message indicating the requested change to theconfiguration of the first network device; as a result of transmittingthe message indicating the requested change to the configuration of thefirst network device, receiving, via the communication interface fromthe computing device, updated configuration information corresponding tothe first network device reflecting that the requested change to theconfiguration of the first network device has been applied to the firstnetwork device; and in response to receiving the updated configurationinformation corresponding to the first network device, displaying, viathe user interface, the updated configuration information correspondingto the first network device.
 2. The wearable device of claim 1, whereinthe first network device is a playback device configured to play backmedia content, and the configuration information comprises configurationinformation related to playing back the media content by the playbackdevice.
 3. The wearable device of claim 2, wherein the requested changeto the configuration of the first network device comprises at least oneof (i) a request to change a volume level of the playback device, (ii) arequest to pause play back of the media content by the playback device,(iii) a request to skip a portion of the play back of the media contentby the playback device, or (iv) a request for the first playback deviceto enter into a group with a second playback device in which the firstand second playback devices are configured for synchronous playback ofthe media content.
 4. The wearable device of claim 1, wherein the seconduser input indicates that a given configuration parameter of the firstnetwork device is to be changed from a first value to a second value. 5.The wearable device of claim 1, wherein the plurality of network devicesincludes a second device, and further comprising program instructionsstored on the non-transitory computer-readable medium that areexecutable by the processor to cause the wearable device to performfunctions comprising: displaying, via the user interface, an indicationof the second network device; receiving, via the user interface, a thirduser input indicating a selection of the second network device; inresponse to receiving the third user input, displaying, via the userinterface, a representation of configuration information correspondingto the second network device that is indicative of a configuration ofthe second network device; receiving, via the user interface, a fourthuser input indicating a requested change to the configuration of thesecond network device; in response to receiving the fourth user input,transmitting, via the communication interface to the computing device, amessage indicating the requested change to the configuration of thesecond network device; as a result of transmitting the messageindicating the requested change to the configuration of the secondnetwork device, receiving, via the communication interface from thecomputing device, updated configuration information corresponding to thesecond network device reflecting that the requested change to theconfiguration of the second network device has been applied to thesecond network device; and in response to receiving the updatedconfiguration information corresponding to the second network device,displaying, via the user interface, the updated configurationinformation corresponding to the second network device.
 6. The wearabledevice of claim 1, wherein the computing device comprises a mobiledevice.
 7. The wearable device of claim 1, further comprising programinstructions stored on the non-transitory computer-readable medium thatare executable by the processor to cause the wearable device to performfunctions comprising: displaying, via the user interface, a selectablegrouping option associated with a given group of network devices thatincludes the first network device and at least one other network deviceof the plurality of network devices in the household; receiving, via theuser interface, a third user input indicating a selection of theselectable grouping option; in response to receiving the third userinput, transmitting, via the communication interface to the computingdevice, a message indicating the selection of the selectable groupingoption; and as a result of transmitting the message indicating theselection of the selectable grouping option, receiving, via thecommunication interface from the computing device, an indication thatthe given group of network devices has been formed.
 8. The wearabledevice of claim 1, wherein the first user input is at least one of (i) atap on the user interface, (ii) a swipe across a portion of the userinterface, or (iii) a shaking of the wearable device, and wherein thesecond user input is at least one of (i) a tap on the user interface,(ii) a swipe across a portion of the user interface, or (iii) a shakingof the wearable device.
 9. A method comprising: receiving, by a wearabledevice from a computing device, respective configuration informationcorresponding to each of a plurality of network devices in a householdthat have been grouped together, wherein the computing device isconfigured to facilitate control of each of the plurality of networkdevices in the household via a data network, and wherein the pluralityof network devices includes a first network device; displaying, via auser interface of the wearable device, an indication of the firstnetwork device; receiving, via the user interface of the wearabledevice, a first user input indicating a selection of the first networkdevice; in response to receiving the first user input, displaying, viathe user interface of the wearable device, a representation ofconfiguration information corresponding to the first network device thatis indicative of a configuration of the first network device; receiving,via the user interface of the wearable device, a second user inputindicating a requested change to the configuration of the first networkdevice; in response to receiving the second user input, transmitting,via a communication interface of the wearable device to the computingdevice, a message indicating the requested change to the configurationof the first network device; as a result of transmitting the messageindicating the requested change to the configuration of the firstnetwork device, receiving, via the communication interface of thewearable device from the computing device, updated configurationinformation corresponding to the first network device reflecting thatthe requested change to the configuration of the first network devicehas been applied to the first network device; and in response toreceiving the updated configuration information corresponding to thefirst network device, displaying, via the user interface of the wearabledevice, the updated configuration information corresponding to the firstnetwork device.
 10. The method of claim 9, wherein the first networkdevice is a playback device configured to play back media content, andthe configuration information comprises configuration informationrelated to playing back the media content by the playback device. 11.The method of claim 10, wherein the requested change to theconfiguration of the first network device comprises at least one of (i)a request to change a volume level of the playback device, (ii) arequest to pause play back of the media content by the playback device,(iii) a request to skip a portion of the play back of the media contentby the playback device, or (iv) a request for the first playback deviceto enter into a group with a second playback device in which the firstand second playback devices are configured for synchronous playback ofthe media content.
 12. The method of claim 9, wherein the plurality ofnetwork devices includes a second device, the method further comprising:displaying, via the user interface of the wearable device, an indicationof the second network device; receiving, via the user interface of thewearable device, a third user input indicating a selection of the secondnetwork device; in response to receiving the third user input,displaying, via the user interface of the wearable device, arepresentation of configuration information corresponding to the secondnetwork device that is indicative of a configuration of the secondnetwork device; receiving, via the user interface of the wearabledevice, a fourth user input indicating a requested change to theconfiguration of the second network device; in response to receiving thefourth user input, transmitting, via the communication interface to thecomputing device, a message indicating the requested change to theconfiguration of the second network device; as a result of transmittingthe message indicating the requested change to the configuration of thesecond network device, receiving, via the communication interface of thewearable device from the computing device, updated configurationinformation corresponding to the second network device reflecting thatthe requested change to the configuration of the second network devicehas been applied to the second network device; and in response toreceiving the updated configuration information corresponding to thesecond network device, displaying, via the user interface of thewearable device, the updated configuration information corresponding tothe second network device.
 13. The method of claim 9, wherein thecomputing device comprises a mobile device.
 14. The method of claim 9,wherein the first user input is at least one of (i) a tap on the userinterface, (ii) a swipe across a portion of the user interface, or (iii)a shaking of the wearable device, and wherein the second user input isat least one of (i) a tap on the user interface, (ii) a swipe across aportion of the user interface, or (iii) a shaking of the wearabledevice.
 15. A non-transitory computer-readable medium having programinstructions stored on the non-transitory computer-readable medium that,when executed by a processor of a wearable device, cause the wearabledevice to perform functions comprising: receiving, from a computingdevice, respective configuration information corresponding to each of aplurality of network devices in a household that have been groupedtogether, wherein the computing device is configured to facilitatecontrol of each of the plurality of network devices in the household viaa data network, and wherein the plurality of network devices includes afirst network device; displaying, via a user interface of the wearabledevice, an indication of the first network device; receiving, via theuser interface of the wearable device, a first user input indicating aselection of the first network device; in response to receiving thefirst user input, displaying, via the user interface of the wearabledevice, a representation of configuration information corresponding tothe first network device that is indicative of a configuration of thefirst network device; receiving, via the user interface of the wearabledevice, a second user input indicating a requested change to theconfiguration of the first network device; in response to receiving thesecond user input, transmitting, via a communication interface of thewearable device to the computing device, a message indicating therequested change to the configuration of the first network device; as aresult of transmitting the message indicating the requested change tothe configuration of the first network device, receiving, via thecommunication interface of the wearable device from the computingdevice, updated configuration information corresponding to the firstnetwork device reflecting that the requested change to the configurationof the first network device has been applied to the first networkdevice; and in response to receiving the updated configurationinformation corresponding to the first network device, displaying, viathe user interface of the wearable device, the updated configurationinformation corresponding to the first network device.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the firstnetwork device is a playback device configured to play back mediacontent, and the configuration information comprises configurationinformation related to playing back the media content by the playbackdevice.
 17. The non-transitory computer-readable medium of claim 16,wherein the requested change to the configuration of the first networkdevice comprises at least one of (i) a request to change a volume levelof the playback device, (ii) a request to pause play back of the mediacontent by the playback device, (iii) a request to skip a portion of theplay back of the media content by the playback device, or (iv) a requestfor the first playback device to enter into a group with a secondplayback device in which the first and second playback devices areconfigured for synchronous playback of the media content.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theplurality of network devices includes a second device, and furthercomprising program instructions stored on the non-transitorycomputer-readable medium that, when executed by the processor of thewearable device, cause the wearable device to perform functionscomprising: displaying, via the user interface of the wearable device,an indication of the second network device; receiving, via the userinterface of the wearable device, a third user input indicating aselection of the second network device; in response to receiving thethird user input, displaying, via the user interface of the wearabledevice, a representation of configuration information corresponding tothe second network device that is indicative of a configuration of thesecond network device; receiving, via the user interface of the wearabledevice, a fourth user input indicating a requested change to theconfiguration of the second network device; in response to receiving thefourth user input, transmitting, via the communication interface to thecomputing device, a message indicating the requested change to theconfiguration of the second network device; as a result of transmittingthe message indicating the requested change to the configuration of thesecond network device, receiving, via the communication interface of thewearable device from the computing device, updated configurationinformation corresponding to the second network device reflecting thatthe requested change to the configuration of the second network devicehas been applied to the second network device; and in response toreceiving the updated configuration information corresponding to thesecond network device, displaying, via the user interface of thewearable device, the updated configuration information corresponding tothe second network device.
 19. The non-transitory computer-readablemedium of claim 15, wherein the computing device comprises a mobiledevice.
 20. The non-transitory computer-readable medium of claim 15,wherein the first user input is at least one of (i) a tap on the userinterface, (ii) a swipe across a portion of the user interface, or (iii)a shaking of the wearable device, and wherein the second user input isat least one of (i) a tap on the user interface, (ii) a swipe across aportion of the user interface, or (iii) a shaking of the wearabledevice.